Testing a configuration change

ABSTRACT

An approach is provided for testing a change (i.e., configuration change) in a configuration of a computing environment. First configurable attributes of a user identifier (ID) of a user are determined. The user ID was received from an administrative user having an administrative user ID providing the administrative user with an authority of an administrator in the computing environment. A temporary simulation user ID (TSID) having second configurable attributes is generated so that the values of respective first and second configurable attributes are identical. The configuration change is associated with the TSID and with no other user ID. Based on the configuration change being associated with the TSID and with no other user ID, a simulation with the change in the configuration applied in the computing environment is performed. The user ID and administrative user ID are unaffected by the configuration change.

This application is a continuation application claiming priority to Ser.No. 13/468,545 filed May 10, 2012, now U.S. Pat. No. 8,738,895 issuedMay 27, 2014.

TECHNICAL FIELD

The present invention relates to a data processing method and system formanaging an information technology system, and more particularly to atechnique for testing a change in a configuration of a computingenvironment by simulating a user in an application.

BACKGROUND

Known information technology (IT) service management software providecustomers with a comprehensive view of IT service management and toolsto optimize end-to-end IT processes. Applications included in known ITservice management software provide self-help for end users; a fullservice desk with incident, problem and change management; computingasset management; security, workflow and user interface designcapabilities for process and screen customization; and/or a productivitytool and database for managing, auditing and coordinating change andconfiguration management processes. Functions provided by current ITservice management software include dynamic login and security profilesand flexible configuration options. The dynamic login and securityprofiles allow a modification of security permissions of a user of anapplication so that resulting changes to the application's permissionaccess and/or behavior occur on a subsequent login of the user. Theflexible configuration options provide dynamic application behaviorbased on various users or groups of users, or based on data values in arecord the user is viewing, through administrative applications, such asan application to design workflow processes. Business logic may beconfigured in known IT service management software so that although allusers have access to the same application, what one user is able to viewor perform may be different from what another user is able to view orperform.

BRIEF SUMMARY

In first embodiments, the present invention provides a method of testinga change in a configuration of a computing environment. The methodincludes a computer receiving a first user identifier (ID) of a firstuser in the computing environment, the first user ID received from asecond user logged into the computing environment using a second user IDspecifying the second user as having an authority of an administrator inthe computing environment. The method further includes the computerdetermining a first set of one or more configurable attributes of thefirst user ID. The method further includes the computer generating atemporary user ID having a second set of one or more configurableattributes so that values of respective configurable attributes in thefirst and second sets of configurable attributes are identical. Themethod further includes the computer receiving the change in theconfiguration of the computing environment. The method further includesthe computer associating the change in the configuration with thetemporary user ID and with no other user ID. The method furtherincludes, based on the change in the configuration being associated withthe temporary user ID and with no other user ID, the computer performinga simulation by tracking modifications to data records made by thetemporary user ID and based on the change in the configuration. Thechange in the configuration does not affect the first and second userIDs. The method further includes, after a completion of the simulation,the computer undoing the modifications to the data records.

In second embodiments, the present invention provides a computer systemincluding a central processing unit (CPU), a memory coupled to the CPU,and a computer-readable, tangible storage device coupled to the CPU. Thestorage device contains instructions that, when carried out by the CPUvia the memory, implement a method of testing a change in aconfiguration of a computing environment. The method includes thecomputer system receiving a first user identifier (ID) of a first userin the computing environment, the first user ID received from a seconduser logged into the computing environment using a second user IDspecifying the second user as having an authority of an administrator inthe computing environment. The method further includes the computersystem determining a first set of one or more configurable attributes ofthe first user ID. The method further includes the computer systemgenerating a temporary user ID having a second set of one or moreconfigurable attributes so that values of respective configurableattributes in the first and second sets of configurable attributes areidentical. The method further includes the computer system receiving thechange in the configuration of the computing environment. The methodfurther includes the computer system associating the change in theconfiguration with the temporary user ID and with no other user ID. Themethod further includes, based on the change in the configuration beingassociated with the temporary user ID and with no other user ID, thecomputer system performing a simulation by tracking modifications todata records made by the temporary user ID and based on the change inthe configuration, the change in the configuration not affecting thefirst and second user IDs. The method further includes, after acompletion of the simulation, the computer system undoing themodifications to the data records.

In third embodiments, the present invention provides a computer programproduct including a computer-readable, tangible storage device andcomputer-readable program instructions stored in the computer-readable,tangible storage device. The computer-readable program instructions,when carried out by a central processing unit (CPU) of a computersystem, implement a method of testing a change in a configuration of acomputing environment. The method includes the computer system receivinga first user identifier (ID) of a first user in the computingenvironment, the first user ID received from a second user logged intothe computing environment using a second user ID specifying the seconduser as having an authority of an administrator in the computingenvironment. The method further includes the computer system determininga first set of one or more configurable attributes of the first user ID.The method further includes the computer system generating a temporaryuser ID having a second set of one or more configurable attributes sothat values of respective configurable attributes in the first andsecond sets of configurable attributes are identical. The method furtherincludes the computer system receiving the change in the configurationof the computing environment. The method further includes the computersystem associating the change in the configuration with the temporaryuser ID and with no other user ID. The method further includes, based onthe change in the configuration being associated with the temporary userID and with no other user ID, the computer system performing asimulation by tracking modifications to data records made by thetemporary user ID and based on the change in the configuration, thechange in the configuration not affecting the first and second user IDs.The method further includes, after a completion of the simulation, thecomputer system undoing the modifications to the data records.

Embodiments of the present invention allow an administrator to quicklyset up a recreate scenario for a customer issue and eliminate theerror-prone manual configuration of a user identifier (ID) to test afix, thereby reducing the time it takes to fix the customer issue.Embodiments of the present invention allow multiple concurrent user IDsimulations, such as for two users configured in the same way, where oneuser is a functioning user and the other user is a non-functioning user.An administrator can walk through actions one-by-one, comparing theresult of each action with the functioning user, as opposed to thenon-functioning user. Furthermore, by the dynamic substitution of atemporary simulation ID with the actual user ID being simulated, anembodiment allows an administrator to simulate actual behavior a problemuser is experiencing without having to obtain the user's password andwithout having to log in as the user. Still further, by allowing thesimulation of a potential fix, an embodiment allows an administrator toquickly run through multiple regression tests to determine if an updateworks, without having to go through a full development to useracceptance testing (UAT) to production cycle. Further yet, an embodimentallows all general users to avoid being impacted by a configurationchange because the change applies only to one or more specifiedtemporary simulation user IDs during the simulation.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 depicts a block diagram of a system for testing a change in aconfiguration of a computing environment, in accordance with embodimentsof the present invention.

FIGS. 2A-2B depict a flowchart of a process of testing a change in aconfiguration of a computing environment, where the process isimplemented in the system of FIG. 1, in accordance with embodiments ofthe present invention.

FIG. 3 is a flowchart of a process of tracking modifications to datarecords made by a temporary simulation ID, in accordance withembodiments of the present invention.

FIGS. 4A-4B depict a flowchart of a process of undoing modifications todata records made by a temporary simulation ID during a simulation, inaccordance with embodiments of the present invention.

FIG. 5 is a flowchart of a process of replacing a temporary simulationID with a simulation user ID, in accordance with embodiments of thepresent invention.

FIG. 6 is a flowchart of a process of performing action(s) in asimulation by applying a proposed configuration change to a temporarysimulation ID, in accordance with embodiments of the present invention.

FIG. 7 is a block diagram of a computer system that is included in thesystem of FIG. 1 and that implements the processes of FIGS. 2A-2B, FIG.3, FIGS. 4A-4B, FIG. 5 and FIG. 6, in accordance with embodiments of thepresent invention.

DETAILED DESCRIPTION Overview

Embodiments of the present invention enable an administrative user (alsoknown as (a.k.a.) an admin user), or another user having appropriateauthority, to temporarily log into a software application with atemporary simulation user ID (TSID) which has configurable attributesthat match configurable attributes of a user ID of another user of theapplication. Configurable attributes of a user ID may include securitygroups and/or person groups to the user ID belongs. Utilization of aTSID may facilitate debugging issues with the application and may allowa simulation of a proposed fix of an issue with the application in alive instance (i.e., production environment), without having to firstcommit the changes, and without having to utilize a development and/orUAT environment. Embodiments of the present invention may be implementedas modifications to program code of a software application or softwareproduct having login capability, security profiles, and flexibleconfiguration options, such as IBM® Service Management, a servicemanagement software suite included in Tivoli® software products offeredby International Business Machines Corporation located in Armonk, N.Y.

An admin user may use the TSID to debug an application in a scenario inwhich a first user is experiencing an issue or defect in a liveproduction instance of the application, whereas a second user is notexperiencing any issues at all in the live instance. If the first useris configured differently from the second user, the utilization of theTSID may allow a debugging of the issue or defect without requiring theadmin user to configure the ID of the admin user to match theconfiguration of the first user, thereby (1) bypassing a need to takeaway the admin user's administrative privileges and requiring anotheradmin user to restore the administrative privileges, (2) avoiding thetime needed to manually view and reconfigure an ID, and (3) eliminatinga possibility of an action against a problematic record in a productioninstance showing up in an audit log as being performed by an admin userwho has reconfigured the admin user ID as a customer ID.

If the first user who is experiencing the issue is configured in thesame way as the second user who is not experiencing the issue, the TSIDmay be utilized to avoid a need to coordinate a schedule between thefirst user and the admin user so that the admin user can view theactions taken to cause the error.

Further, the admin user may utilize the TSID to test a proposedconfiguration change (a.k.a. a fix) to resolve issues in an applicationin a production instance, thereby avoiding a need for testing the fix ona development server, moving the fix to a UAT server for customerverification, and then scheduling a change to the production instance.Still further, the utilization of the TSID may allow testing of a fix ina production instance, where the fix addresses classes of issues, suchas performance issues, that are not easily or quickly reproducible in adevelopment environment.

System for Testing a Configuration Change

FIG. 1 depicts a block diagram of a system for testing a change in aconfiguration of a computing environment, in accordance with embodimentsof the present invention. System 100 includes a computer system 102,which runs a software-based configuration change testing tool 104 and asoftware-based application 106. Configuration change testing tool 104receives a simulation admin user ID (SAID) 108 and simulation user ID(SUID) 110-1 . . . SUID 110-N, where N≧1. The SAID 108 is the ID of anadmin user of application 106. SUID 110-1 . . . SUID 110-N are user IDsof N respective users of application 106.

Configuration change testing tool 104 and application 106 access aconfigurable attributes data repository 112 that includes configurableattributes of SUID 110-1 . . . SUID 110-N, such as security profile(s)of each of SUID 110-1 . . . SUID 110-N and/or person group(s) to whicheach of SUID 110-1 . . . SUID 110-N belongs. Configuration changetesting tool 104 generates TSID 114-1 . . . TSID 114-N, in one-to-onecorrespondence with SUID 110-1 . . . SUID 110-N so that value(s) ofconfigurable attribute(s) of each generated TSID match value(s) ofrespective configurable attribute(s) of the corresponding SUID in SUID110-1 . . . SUID 110-N. For example, TSID 114-1 may have configurableattributes whose values indicate that TSID 114-1 has security profile Pand belongs to person group G, and corresponding SUID 110-1 hasconfigurable attributes whose values indicate that SUID 110-1 also hassecurity profile P and belongs to person group G (i.e., SUID 110-1 hasthe security profile and belongs to the person group that match thesecurity profile and person group, respectively, of TSID 114-1). Theconfigurable attributes of TSID 114-1 . . . TSID 114-N are included inconfigurable attributes data repository 112.

In one embodiment, configuration change testing tool 104 receives aproposed configuration change 116 (a.k.a. a fix) to a computingenvironment that addresses an issue or defect in application 106.Configuration change testing tool 104 tests the proposed configurationchange 116 as described below in the discussion of FIGS. 2A-2B.

In one embodiment, configuration change testing tool 104 performs asimulation of one or more users of application 106 who are identified bySUID 110-1 . . . SUID 110-N, where the simulation includes configurationchange testing tool 104 utilizing TSID 114-1 . . . 114-N to log onapplication 106 and perform action(s) by application 106. The action(s)performed by application 106 may be provided at least in part byproposed configuration change 116. The action(s) performed byapplication 106 may include storing and/or accessing one or moreconfigurable attributes from configurable attributes data repository112. Configuration change testing tool 104 may track data records (e.g.,database records) that are modified during the simulation of the one ormore users and may store the modified data records in a modified datarecords repository 118.

Although not shown in FIG. 1, computer system 102 may be coupled to anemail system, so that configuration change testing tool 104 may trackemails generated by TSID 114-1 . . . TSID 114-N and prevent emails sentby general users from being commingled with emails generated as a resultof a simulation of SUID 110-1 . . . SUID 110-N.

The functionality of the components shown in FIG. 1 are described belowin more detail in the discussions of FIGS. 2A-2B, FIG. 3, FIGS. 4A-4B,FIG. 5 and FIG. 6.

Process for Testing a Configuration Change

FIGS. 2A-2B depict a flowchart of a process of testing a change in aconfiguration of a computing environment, where the process isimplemented in the system of FIG. 1, in accordance with embodiments ofthe present invention. The process for testing a configuration change bysimulating a user begins at step 200. In step 202, configuration changetesting tool 104 (see FIG. 1) receives from an admin user (1) a commandto initiate a simulation of one or more users of application 106 (seeFIG. 1) and (2) a selection of one or more SUIDs from SUID 110-1 . . .SUID 110-N (see FIG. 1), where each selected SUID identifies arespective user being simulated. Hereinafter, in the discussion of FIGS.2A-2B, the admin user from whom the command and selection of the SUIDsis received in step 202 is referred to simply as “the admin user.”Hereinafter, a simulation of a user of application 106 is also referredto as a simulation of the SUID of the user.

The remaining steps of FIGS. 2A-2B describe a simulation of one SUID,but those skilled in the art will recognize how each subsequent step maybe modified so that a plurality of SUIDs may be simulated.

In step 204, configuration change testing tool 104 (see FIG. 1)determines whether the admin user has authority to perform thesimulation of the SUID. If configuration change testing tool 104 (seeFIG. 1) determines in step 204 that the admin user does not have theauthority to perform the simulation of the SUID, then the No branch ofstep 204 is taken and step 206 is performed. In step 206, configurationchange testing tool 104 (see FIG. 1) disallows the simulation of theSUID and subsequently, the process of FIGS. 2A-2B ends at step 208. Inone embodiment, configuration change testing tool 104 (see FIG. 1) instep 206 prevents a presentation of an option to simulate the SUID. Inanother embodiment, configuration change testing tool 104 (see FIG. 1)in step 206 presents an error message to the admin user when the SAIDattempts to invoke the simulation.

If configuration change testing tool 104 (see FIG. 1) determines in step204 that the admin user has the authority to perform the simulation ofthe SUID, then the Yes branch of step 204 is taken and step 210 isperformed.

In step 210, configuration change testing tool 104 (see FIG. 1)generates a TSID having configurable attributes whose values match thevalues of configurable attributes of the SUID. In an alternateembodiment, configuration change testing tool 104 (see FIG. 1) generatesa TSID in step 210 that has one or more configurable attributes thatcomprise a proper subset of a set of configurable attributes of theSUID, where the one or more configurable attributes of the TSID havevalue(s) that match value(s) of the corresponding one or moreconfigurable attributes of the SUID. Hereinafter, in the discussion ofFIGS. 2A-2B, the TSID generated in step 210 is referred to simply as theTSID.

In one embodiment, configuration change testing tool 104 (see FIG. 1)(1) iterates over configurable attributes of each SUID in SUID 110-1 . .. SUID 110-N (see FIG. 1); (2) dynamically creates new respective TSIDsin TSID 114-1 . . . TSID 114-N (see FIG. 1), each TSID having values ofconfigurable attributes that match values of configurable attributes ofthe corresponding SUID; and (3) returns name and password of eachcreated TSID to the SAID.

In one embodiment, step 210 includes the configuration change testingtool 104 (see FIG. 1) prompting and receiving from the SAID a specifiedemail address to which notifications are to be sent, so that any emailgenerated by the TSID is directed to the specified email address,instead of to a user ID of a general user of application 106 (see FIG.1). The restriction of the recipient of emails originating from the TSIDis described below relative to step 218.

In step 212, configuration change testing tool 104 (see FIG. 1) opens awindow of application 106 (see FIG. 1) with the TSID logged in toapplication 106 (see FIG. 1). In one embodiment, configuration changetesting tool 104 (see FIG. 1) opens multiple windows to log in multipleTSIDs, respectively, into application 106, thereby allowingconfiguration change testing tool 104 (see FIG. 1) to address cases inwhich errors are generated via multiple users for the same customerbeing logged in at the same time and working on the same problem ticketsor in the same application.

In step 214, configuration change testing tool 104 (see FIG. 1) receivesa proposed configuration change 116 (see FIG. 1) (i.e., a proposedchange in the configuration of the computing environment of application106 (see FIG. 1)).

In step 216, configuration change testing tool 104 (see FIG. 1)associates the proposed configuration change 116 (see FIG. 1) with theTSID. For example, configuration change testing tool 104 (see FIG. 1)stores in a data repository coupled to computer system 102 (see FIG. 1)a specification of the proposed configuration change 116 (see FIG. 1)and the TSID.

In step 218, configuration change testing tool 104 (see FIG. 1) preventsa commingling of emails and/or other communications sent by generalusers of application 106 (see FIG. 1) with emails and/or othercommunications generated as a result of the simulation of the SUID. Inone embodiment, during the simulation of the SUID, configuration changetesting tool 104 (see FIG. 1) tracks any emails generated by the TSIDand dynamically replaces the recipient email addresses (e.g., in the to,cc, and bcc fields) with another email address associated with the TSID.The configuration change testing tool 104 (see FIG. 1) receives theother email address from an entry provided by the admin user prior tostep 218 (e.g., in step 202, at the initiation of the simulation). Byreplacing the recipient email addresses with the other email addressassociated with the TSID, customer users are prevented from receivingemail generated during the simulation of the SUID, which would bepotentially confusing to the customer users. In one embodiment, the TSIDis configured prior to step 218 so that the TSID does not receive emailssent to the person group to which the TSID belongs, thereby eliminatingconfusion in the output of debugging.

Prior to step 220, the admin user or another administrative user mayconfigure the configuration change testing tool 104 (see FIG. 1) togenerate additional logging information for the TSID. In step 220, ifconfiguration change testing tool 104 (see FIG. 1) is configured foradditional logging, then configuration change testing tool 104 (seeFIG. 1) initiates additional logging output for the TSID only, and notfor other users of application 106 (see FIG. 1). For example,configuration change testing tool 104 (see FIG. 1) may append anadditional logger to the main system logger(s), where the additionallogger provides logging information at a more detailed level ofgranularity (e.g., more SQL outputted, etc.). As a result of appendingthe additional logger, the configuration change testing tool 104 (seeFIG. 1) may output to a specific log window the modifications to thelogs while the SAID is performing the simulation.

Following step 220, the process of FIGS. 2A-2B continues with step 222in FIG. 2B. In step 222, in a live instance of application 106 (see FIG.1), configuration change testing tool 104 (see FIG. 1) performsaction(s) in the simulation of the SUID by applying the proposedconfiguration change 116 (see FIG. 1) to the TSID, but not to other userIDs of application 106 (see FIG. 1).

For example, in the live instance in step 222, the SAID may test one ormore proposed configuration changes to the computing environment ofapplication 106 (see FIG. 1), including the proposed configurationchange 116 (see FIG. 1) to test whether a performance improvementdecreases response time in application 106 (see FIG. 1) to an acceptablelevel. To perform the aforementioned test of the performanceimprovement, the SAID may invoke a command to denote which configurationchanges are temporary and to which TSID in TSID 114-1 . . . TSID 114-N(see FIG. 1) the configuration changes apply.

For instance, the SAID may change an original SQL query fragment toanother SQL query fragment to determine if the change improvesperformance (e.g., the change in the SQL query fragment is the proposedconfiguration change 116 in FIG. 1). Configuration change testing tool104 (see FIG. 1) leaves the original SQL query fragment unchanged, butcreates the other (i.e., modified) SQL query fragment and receives fromthe SAID a specification of the TSID(s) in TSID 114-1 . . . TSID 114-N(see FIG. 1) to which the other SQL query fragment applies. Therefore,when the logic of application 106 (see FIG. 1) enters the code path inwhich the original SQL query fragment should be dynamically applied,configuration change testing tool 104 (see FIG. 1) checks whether thereexists a modified SQL query fragment for the TSID that is logged intoapplication 106 (see FIG. 1). In the example in this paragraph,configuration change testing tool 104 (see FIG. 1) determines that themodified SQL query fragment exists for the TSID that is logged intoapplication 106 (see FIG. 1), and in response, utilizes the modified SQLquery fragment in the code path. If the configuration change testingtool 104 (see FIG. 1) had determined that a modified SQL query fragmentdid not exist for the logged in TSID, then the code path would haveutilized the original SQL query fragment.

The feature described in step 222 allows the configuration changetesting tool 104 (see FIG. 1) to apply the proposed configuration change116 (see FIG. 1) only to the TSID while the proposed configurationchange 116 (see FIG. 1) is being tested, whereas other users ofapplication 106 (see FIG. 1) experience no impact from the proposedconfiguration change 116 (see FIG. 1).

It should be noted that the configuration change testing tool 104 (seeFIG. 1) checking whether there exists a proposed configuration changefor a TSID logged into application 106 (see FIG. 1) is required only ifconfiguration change testing tool 104 (see FIG. 1) determines that atleast one simulation of a SUID included in SUID 110-1 . . . SUID 110-N(see FIG. 1) is active, thereby reducing the impact that theaforementioned checking has on the performance of application 106 (seeFIG. 1).

In step 224, configuration change testing tool 104 (see FIG. 1) tracksmodifications to data records made by the TSID as part of the simulationof the SUID. The configuration change testing tool 104 (see FIG. 1)stores the tracked modifications of the data records in modified datarecords repository 118 (see FIG. 1). Each modification to a data recordbeing tracked in step 224 may be an insertion of the data record into adatabase, a deletion of the data record from the database, or an updateof the data record in the database.

While the SAID is performing actions during a simulation of the SUID byutilizing the TSID, configuration change testing tool 104 (see FIG. 1)may track the modifications of the data records in step 224 by storingindications of the modifications in temporary storage files. In oneembodiment, modified data records repository 118 (see FIG. 1) includesthe temporary storage files that store the indications of themodifications of the data records tracked in step 224.

For a modification that is an update to or a delete from a database,configuration change testing tool 104 (see FIG. 1) exports the datarecord. For a modification that is an insert to a database,configuration change testing tool 104 (see FIG. 1) stores the primarykey of the newly created data record. Known multi-user applicationstrack the user who is currently logged in. The configuration changetesting tool 104 (see FIG. 1) uses the tracking of the user who iscurrently logged in to determine whether the tracked user is identifiedwith a TSID included in TSID 114-1 . . . TSID 114-N (see FIG. 1). If thetracked user is identified with a TSID, then configuration changetesting tool 104 (see FIG. 1) tracks the TSID's interactions with thedatabase.

In some cases regarding troubleshooting an issue with application 106(see FIG. 1), it may be necessary to invoke actions as the SUID of theactual user who is experiencing the issue in order to re-create thescenario in which the issue arises. When the simulation of the SUIDbegins, the configuration change testing tool 104 (see FIG. 1) mayreceive a selection of an option (or retrieve a configuration from aproperty file (not shown in FIG. 1)) to execute all the actions as theSUID, rather than as the TSID, even though the SAID is logged in as theTSID. For example, in the case in which user IDs for User 1 and User 2are configured in exactly the same way, and User 1 experiences an issuewith application 106 (see FIG. 1) while User 2 does not experience theissue, the admin user may select an option so that the configurationchange testing tool 104 (see FIG. 1) invokes actions as the user ID ofUser 1, rather than as the TSID. In one embodiment, to implement theexecution of actions as the SUID rather than as the TSID, theconfiguration change testing tool 104 (see FIG. 1) intercepts eachaction performed by the TSID and substitutes the value of the SUID inany modifications (e.g., SQL queries, etc.) before executing a commandthat invokes the action.

The selection of the option to invoke actions as the SUID rather than asthe TSID may be advantageous in cases in which an element orcharacteristic of the SUID itself causes the issue, and the element ofcharacteristic may not be immediately apparent. For example, the lengthof the SUID may cause an issue in a nested, complex query, and theresulting error message may be cryptic. As other examples, a specialcharacter in the SUID may cause the issue, or the records associated tothe SUID may cause the issue. For instance, queries may be made usingthe SUID, and the data in the records accessed by the queries may havespecial characters that are causing the issue. If configuration changetesting tool 104 (see FIG. 1) issued the queries as the TSID, theassociated records returned may be different from the records returnedhad the queries been issued as the SUID, even though the values of theconfigurable attributes of the TSID are the same as the values of theconfigurable attributes of the SUID. Since the records returned whenissuing the queries as the TSID may be different from the recordsreturned when issuing the queries as the SUID, the issue may not bereproduced when issuing the queries as the TSID.

In step 226, if configuration change testing tool 104 (see FIG. 1)determines that the proposed configuration change 116 (see FIG. 1)should be made permanent (e.g., by receiving an invocation of a commandfrom the SAID), then the Yes branch of step 226 is taken and step 228 isperformed. In step 228, configuration change testing tool 104 (seeFIG. 1) permanently applies the proposed configuration change 116 (seeFIG. 1) to other users (e.g., all users) of application 106 (see FIG.1). For example, configuration change testing tool 104 (see FIG. 1) instep 228 replaces the original SQL query fragment with the modified SQLquery fragment and removes the copy of the modified SQL query fragmentassociated with the TSID(s), thereby subsequently applying the modifiedSQL query fragment to all users of application 106 (see FIG. 1). Itshould be noted that some configuration changes require a restart ofapplication 106 (see FIG. 1) in order to take effect with the otherusers, and therefore waiting for a Change window may delay making such aconfiguration change permanent in step 228. Otherwise, permanentlyapplying the proposed configuration change 116 (see FIG. 1) in step 228is immediate.

Returning to step 226, if configuration change testing tool 104 (seeFIG. 1) determines that the proposed configuration change 116 (seeFIG. 1) should not be made permanent, then the No branch of step 226 istaken and step 230 is performed. Step 230 also follows step 228.

In step 230, configuration change testing tool 104 (see FIG. 1) receivesa command from the SAID to end the simulation of the SUID.

In step 232, and in response to receiving the command to end thesimulation in step 230, configuration change testing tool 104 (seeFIG. 1) stops tracking modifications to data records made by the TSID.

In step 234 and in response to receiving the command to end thesimulation in step 230, configuration change testing tool 104 (seeFIG. 1) undoes the modifications to the data records performed by theTSID and tracked in step 224. Undoing the modifications includesconfiguration change testing tool 104 (see FIG. 1) utilizing thetemporary storage files in which the indications of the modificationswere stored in step 224. If a tracked modification included a datarecord being updated or deleted, then in step 234, configuration changetesting tool 104 (see FIG. 1) re-imports the exported data record backinto the database. If a tracked modification included a data recordbeing inserted, then configuration change testing tool 104 (see FIG. 1)in step 234 deletes the inserted data record from the database based onthe stored primary key.

Some inserted data records (e.g., Incident or Change ticket data) arecomplex, with data being inserted into multiple tables. For such complexinserted data records that are classified as transactional data,configuration change testing tool 104 (see FIG. 1) does not delete thedata records to undo the modification; instead, configuration changetesting tool 104 (see FIG. 1) changes the status of the data records tocanceled or otherwise deactivated.

In step 236, configuration change testing tool 104 (see FIG. 1) logs outthe TSID and closes the application window that was opened in step 212(see FIG. 2A). Also in step 236, configuration change testing tool 104(see FIG. 1) closes any additional logging window that may have beenopened in step 220 (see FIG. 2A).

In step 238, configuration change testing tool 104 (see FIG. 1) removesor otherwise deactivates the TSID. Also in step 238, configurationchange testing tool 104 (see FIG. 1) removes values of configurableattributes that associate the TSID with particular groups, such as theassociation between the TSID and the person group(s) to which the SUIDbelongs.

The process of FIGS. 2A-2B ends at step 240. After step 240, the processof FIGS. 2A-2B may be repeated to simulate another SUID included in SUID110-1 . . . 110-N (see FIG. 1) by generating and utilizing another TSIDincluded in TSID 114-1 . . . TSID 114-N (see FIG. 1).

In an alternate embodiment, the process of FIGS. 2A-2B includes thetracking of modifications performed by a TSID in step 224 (see FIG. 2A)to debug an issue with application 106 (see FIG. 1), but does notinclude receiving proposed configuration change 116 (see FIG. 1) in step214 (see FIG. 2A), associating the proposed configuration change withthe TSID in step 216 (see FIG. 2A), testing the proposed configurationchange in step 222, determining whether or not to make the proposedconfiguration change permanent in step 226 and making the proposedconfiguration change permanent in step 228.

FIG. 3 is a flowchart of a process of tracking modifications to datarecords made by a temporary simulation ID, in accordance withembodiments of the present invention. The process of trackingmodifications to data records made by a TSID begins at step 300. In oneembodiment, the process of FIG. 3 is included in step 224 in FIG. 2B.Hereinafter in the discussion of FIG. 3, the TSID refers to the TSIDgenerated in step 210 (see FIG. 2A) and the SUID refers to the SUIDbeing simulated in the process of FIGS. 2A-2B. In step 302, ifconfiguration change testing tool 104 (see FIG. 1) determines that theTSID initiated an update of a database record or initiated a deletion ofa database record, then the Yes branch of step 302 is taken and step 304is performed.

In step 304, configuration change testing tool 104 (see FIG. 1) exportsinto a temporary storage file the database record whose update ordeletion is determined to be initiated in step 302.

In step 306, configuration change testing tool 104 (see FIG. 1) performsthe update of the database record if configuration change testing tool104 (see FIG. 1) determined in step 302 that the TSID initiated anupdate, or performs the deletion of the database record if configurationchange testing tool 104 (see FIG. 1) determined in step 302 that theTSID initiated a deletion.

Returning to step 302, if configuration change testing tool 104 (seeFIG. 1) determines that the TSID did not initiate a database recordupdate or deletion, then the No branch of step 302 is taken and step 308is performed. In step 308, if configuration change testing tool 104 (seeFIG. 1) determines that the TSID initiated an insert of a databaserecord, then the Yes branch of step 308 is taken and step 310 isperformed. In step 310, configuration change testing tool 104 (seeFIG. 1) performs the insert of the database record whose initiation wasdetermined in step 308. In step 312, configuration change testing tool104 (see FIG. 1) stores in a temporary storage file the primary key anddatabase table of the database record newly inserted in step 310.Following step 312, the process of FIG. 3 ends at step 314.

Returning to step 308, if configuration change testing tool 104 (seeFIG. 1) determines that the TSID did not initiate a database recordinsert, then the process of FIG. 3 ends at step 314.

The process of FIG. 3 also ends at step 314 following step 306.

In one embodiment, the process of FIG. 3 is repeated for one or moreother modifications of database records.

FIGS. 4A-4B depict a flowchart of a process of undoing modifications todata records made by a temporary simulation ID during a simulation, inaccordance with embodiments of the present invention. The process ofundoing modifications to data records made by a TSID during a simulationof a SUID begins at step 400. In one embodiment, the process of FIGS.4A-4B is included in step 234 in FIG. 2B and follows the process of FIG.3. Hereinafter, in the discussion of FIGS. 4A-4B, the TSID refers to theTSID generated in step 210 (see FIG. 2A) and the SUID refers to the SUIDbeing simulated in the process of FIGS. 2A-2B. In step 402,configuration change testing tool 104 (see FIG. 1) retrieves the nexttracked modification from the temporary storage file in which themodification was stored in step 224 (see FIG. 2B). Hereinafter, in thediscussion of FIGS. 4A-4B, the next tracked modification retrieved instep 402 is also referred to simply as “the tracked modification.”

In step 404, if configuration change testing tool 104 (see FIG. 1)determines that the tracked modification applies to transactional datain a transactional record, then the Yes branch of step 404 is taken andstep 406 is performed. In step 406, configuration change testing tool104 (see FIG. 1) sets the status of the transactional record tocanceled.

In step 408, if configuration change testing tool 104 (see FIG. 1)determines that another tracked modification (i.e., another modificationthat had been tracked in step 224 in FIG. 2B) has not yet been retrievedin step 402, then the Yes branch of step 408 is taken and the process ofFIGS. 4A-4B is repeated starting at step 402. If configuration changetesting tool 104 (see FIG. 1) determines in step 408 that no othertracked modification remains to be retrieved from the temporary storagefile, then the No branch of step 408 is taken and the process of FIGS.4A-4B ends at step 410.

Returning to step 404, if configuration change testing tool 104 (seeFIG. 1) determines that the tracked modification does not apply totransactional data, then the No branch of step 404 is taken and step 412is performed.

In step 412, if configuration change testing tool 104 (see FIG. 1)determines that the tracked modification is an update or a deletion of adatabase record, then the Yes branch of step 412 is taken and step 414is performed. In step 414, configuration change testing tool 104 (seeFIG. 1) re-imports the database record that had been exported in step304 (see FIG. 3). After step 414, the process of FIGS. 4A-4B continueswith step 408, as described above.

Returning to step 412, if configuration change testing tool 104 (seeFIG. 1) determines the tracked modification is not an update or deletionof a database record, then the No branch of step 412 is taken and step416 in FIG. 4B is performed.

In step 416, if configuration change testing tool 104 (see FIG. 1)determines that the tracked modification is an insert of a databaserecord, then the Yes branch of step 416 is taken and step 418 isperformed. In step 418, configuration change testing tool 104 (seeFIG. 1) retrieves from the temporary storage file the primary key anddatabase table of the newly inserted record (i.e., the database recordinserted in step 310 (see FIG. 3)). The aforementioned temporary storagefile from which the primary key and database table are retrieved in step418 is the temporary storage file into which the primary key anddatabase table were stored in step 312 (see FIG. 3).

In step 420, configuration change testing tool 104 (see FIG. 1) deletesthe newly inserted database record based on the primary key and databasetable retrieved in step 418.

In step 422, if configuration change testing tool 104 (see FIG. 1)determines that another tracked modification (i.e., another modificationthat had been tracked in step 224 in FIG. 2B) has not yet been retrievedin step 402 (see FIG. 4A), then the Yes branch of step 422 is taken andthe process of FIGS. 4A-4B is repeated starting at step 402 (see FIG.4A). If configuration change testing tool 104 (see FIG. 1) determines instep 422 that no other tracked modification remains to be retrieved fromthe temporary storage file, then the No branch of step 422 is taken andthe process of FIGS. 4A-4B ends at step 424.

Returning to step 416, if configuration change testing tool 104 (seeFIG. 1) determines that the tracked modification is not an insert of adatabase record, then the No branch of step 416 is taken and step 422 isperformed, as described above.

FIG. 5 is a flowchart of a process of replacing a temporary simulationID with a simulation user ID, in accordance with embodiments of thepresent invention. The process of replacing a TSID with a SUID starts atstep 500. In one embodiment, the steps in the process of FIG. 5 replacestep 222 in FIG. 2B. Hereinafter, in the discussion of FIG. 5, the TSIDrefers to the TSID generated in step 210 (see FIG. 2A) and the SUIDrefers to the SUID being simulated in the process of FIGS. 2A-2B.

In step 502, if configuration change testing tool 104 (see FIG. 1)determines that the admin user needs to invoke actions in application106 (see FIG. 1) as the SUID rather than the TSID, then the Yes branchof step 502 is taken and step 504 is performed. Prior to performing step502 and taking the Yes branch of step 502, configuration change testingtool 104 (see FIG. 1) receives a selection of an option to invoke allactions in application 106 (see FIG. 1) as the SUID during a simulationrather than as the TSID, even though the TSID is logged into application106 (see FIG. 1). Alternately, configuration change testing tool 104(see FIG. 1) may retrieve a configuration from a property file thatindicates that all actions in application 106 (see FIG. 1) are to beexecuted as the SUID rather than as the TSID.

Again, invoking actions as the SUID rather than as the TSID may beadvantageous in debugging an issue in application 106 (see FIG. 1) incases in which an element or characteristic of the SUID itself causesthe issue, and the element of characteristic may not be immediatelyapparent (e.g., issues caused by the length of the SUID, a specialcharacter in the SUID, or records associated with the SUID).

In step 504, if configuration change testing tool 104 (see FIG. 1)determines that the SUID is logged in by the user who is identified bythe SUID, then the Yes branch of step 504 is taken and step 506 isperformed.

In step 506, configuration change testing tool 104 (see FIG. 1) presentsa warning to the user identified by the SUID about an upcoming automaticlog out after a specified time period that is configurable. For example,the warning may state “Please save your work within the next X minutes,as your user ID will be logged out for troubleshooting purposes.” Thewarned user may use the specified time period to save any updates orperform other actions before the automatic log out. Following thepresentation of the warning, configuration change testing tool 104 (seeFIG. 1) automatically logs out the user after the specified time periodelapses.

In an alternate embodiment, in step 506, configuration change testingtool 104 (see FIG. 1) prevents the continuance of the simulation andsubsequently ends the process of FIG. 5.

Step 508 follows step 506 and also follows a determination by theconfiguration change testing tool 104 (see FIG. 1) in step 504 that theSUID is not logged into application 106 (see FIG. 1). In step 508,configuration change testing tool 104 (see FIG. 1) disallows the SUIDfrom logging into (or logging back into) application 106 (see FIG. 1)for the duration of the simulation.

In step 510, configuration change testing tool 104 (see FIG. 1) (1)intercepts dynamically generated command(s) that would have invokedaction(s) in application 106 (see FIG. 1) for the TSID in step 222 (seeFIG. 2B); (2) replaces the TSID with the SUID, and (3) invokes theaction(s) in application 106 (see FIG. 1) for the SUID instead of theTSID.

In step 512, configuration change testing tool 104 (see FIG. 1) receivesa command from the SAID to end the simulation. In step 514,configuration change testing tool 104 (see FIG. 1) allows the SUID tolog into application 106 (see FIG. 1) again. Following step 514, theprocess of FIG. 5 ends at step 516.

Returning to step 502, if configuration change testing tool 104 (seeFIG. 1) determines that the admin user does not need to invoke action(s)as the SUID instead of the TSID, then the No branch of step 502 istaken, and the process of FIG. 5 ends at step 516.

FIG. 6 is a flowchart of a process of performing action(s) in asimulation by applying a proposed configuration change to a temporarysimulation ID, in accordance with embodiments of the present invention.The process of performing action(s) in a simulation by applying theproposed configuration change 116 (see FIG. 1) to a TSID only begins atstep 600. In one embodiment, the process of FIG. 6 is included in step222 (see FIG. 2B). Hereinafter, in the discussion of FIG. 6, the TSIDrefers to the TSID generated in step 210 (see FIG. 2A) and the SUIDrefers to the SUID being simulated in the process of FIGS. 2A-2B.

In step 602, configuration change testing tool 104 (see FIG. 1) receivesa specification of proposed configuration change(s) including proposedconfiguration change 116 (see FIG. 1). Also in step 602, configurationchange testing tool 104 (see FIG. 1) receives TSID(s) to which thereceived proposed configuration change(s) apply.

In step 604, configuration change testing tool 104 (see FIG. 1)determines that at least one simulation of a SUID is active.

In step 606, configuration change testing tool 104 (see FIG. 1)intercepts instances of application 106 (see FIG. 1) that useconfiguration(s) to be changed by the proposed configuration change(s)received in step 602.

If configuration change testing tool 104 (see FIG. 1) determines in step608 that the user logged into application 106 (see FIG. 1) matches theTSID (i.e., the logged in user is identified by a user ID that matchesthe TSID in terms of values of configurable attributes), then the Yesbranch of step 608 is taken and step 610 is performed.

In step 610, configuration change testing tool 104 (see FIG. 1) performsdynamically generated command(s) using the proposed configurationchange(s) received in step 602.

In step 612, configuration change testing tool 104 (see FIG. 1) receivesa command to make the proposed configuration change(s) permanent.

In step 614, configuration change testing tool 104 (see FIG. 1)determines that no simulation of a SUID is active.

In step 616, configuration change testing tool 104 (see FIG. 1) haltsthe interception of instances of application 106 (see FIG. 1) that useconfiguration(s) to be changed by the proposed configuration change(s).The process of FIG. 6 ends at step 618.

Returning to step 608, if configuration change testing tool 104 (seeFIG. 1) determines that the user logged into application 106 (seeFIG. 1) does not match the TSID, then the No branch of step 608 istaken, and the process of FIG. 6 continues with step 614, as describedabove.

Computer System

FIG. 7 is a block diagram of a computer system that is included in thesystem of FIG. 1 and that implements the processes of FIGS. 2A-2B, FIG.3, FIGS. 4A-4B, FIG. 5 and FIG. 6, in accordance with embodiments of thepresent invention. Computer system 102 generally comprises a centralprocessing unit (CPU) 702, a memory 704, an input/output (I/O) interface706, and a bus 708. Further, computer system 102 is coupled to I/Odevices 710 and a computer data storage unit 712. CPU 702 performscomputation and control functions of computer system 102, includingcarrying out instructions included in program code 714 to perform amethod of testing a configuration change by simulating a user, where theinstructions are carried out by CPU 702 via memory 704. CPU 702 maycomprise a single processing unit, or be distributed across one or moreprocessing units in one or more locations (e.g., on a client andserver). In one embodiment, program code 714 includes code for theconfiguration change testing tool 104 (see FIG. 1) for testing aconfiguration change.

Memory 704 may comprise any known computer-readable storage medium,which is described below. In one embodiment, cache memory elements ofmemory 704 provide temporary storage of at least some program code(e.g., program code 714) in order to reduce the number of times codemust be retrieved from bulk storage while instructions of the programcode are carried out. Moreover, similar to CPU 702, memory 704 mayreside at a single physical location, comprising one or more types ofdata storage, or be distributed across a plurality of physical systemsin various forms. Further, memory 704 can include data distributedacross, for example, a local area network (LAN) or a wide area network(WAN).

I/O interface 706 comprises any system for exchanging information to orfrom an external source. I/O devices 710 comprise any known type ofexternal device, including a display device (e.g., monitor), keyboard,mouse, printer, speakers, handheld device, facsimile, etc. Bus 708provides a communication link between each of the components in computersystem 102, and may comprise any type of transmission link, includingelectrical, optical, wireless, etc.

I/O interface 706 also allows computer system 102 to store information(e.g., data or program instructions such as program code 714) on andretrieve the information from computer data storage unit 712 or anothercomputer data storage unit (not shown). Computer data storage unit 712may comprise any known computer-readable storage medium, which isdescribed below. For example, computer data storage unit 712 may be anon-volatile data storage device, such as a magnetic disk drive (i.e.,hard disk drive) or an optical disc drive (e.g., a CD-ROM drive whichreceives a CD-ROM disk).

Memory 704 and/or storage unit 712 may store computer program code 714that includes instructions that are carried out by CPU 702 via memory704 to test a configuration change. Although FIG. 7 depicts memory 704as including program code 714, the present invention contemplatesembodiments in which memory 704 does not include all of code 714simultaneously, but instead at one time includes only a portion of code714.

Further, memory 704 may include other systems not shown in FIG. 7, suchas an operating system (e.g., Linux®) that runs on CPU 702 and providescontrol of various components within and/or connected to computer system102. Linux is a registered trademark of Linus Torvalds in the UnitedStates, other countries, or both.

Storage unit 712 and/or one or more other computer data storage units(not shown) that are coupled to computer system 102 may store modifieddata records repository 118 (see FIG. 1), configurable attributes datarepository 112 (see FIG. 1) and/or TSIDS 114-1 . . . 114-N (see FIG. 1)generated using the process of FIGS. 2A-2B.

As will be appreciated by one skilled in the art, in a first embodiment,the present invention may be a system; in a second embodiment, thepresent invention may be a method; and in a third embodiment, thepresent invention may be a computer program product. A component of anembodiment of the present invention may take the form of an entirelyhardware-based component, an entirely software component (includingfirmware, resident software, micro-code, etc.) or a component combiningsoftware and hardware sub-components that may all generally be referredto herein as a “module”.

An embodiment of the present invention may take the form of a computerprogram product embodied in one or more computer-readable medium(s)(e.g., memory 704 and/or computer data storage unit 712) havingcomputer-readable program code (e.g., program code 714) embodied orstored thereon.

Any combination of one or more computer-readable mediums (e.g., memory704 and computer data storage unit 712) may be utilized. The computerreadable medium may be a computer-readable signal medium or acomputer-readable storage medium. In one embodiment, thecomputer-readable storage medium is a computer-readable storage deviceor computer-readable storage apparatus. A computer-readable storagemedium may be, for example, but not limited to, an electronic, magnetic,optical, electromagnetic, or semiconductor system, apparatus, device orany suitable combination of the foregoing. A non-exhaustive list of morespecific examples of the computer-readable storage medium includes: aportable computer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a portable compact disc read-only memory (CD-ROM), anoptical storage device, a magnetic storage device, or any suitablecombination of the foregoing. In the context of this document, acomputer-readable storage medium may be a tangible medium that cancontain or store a program (e.g., program 714) for use by or inconnection with a system, apparatus, or device for carrying outinstructions. Each of the terms “computer-readable storage medium,”“computer-readable storage device,” and “computer-readable, tangiblestorage device” as used herein, is not to be construed as beingtransitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

A computer readable signal medium may include a propagated data signalwith computer-readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electromagnetic, optical, or any suitable combination thereof. Acomputer-readable signal medium may be any computer-readable medium thatis not a computer-readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with asystem, apparatus, or device for carrying out instructions.

Program code (e.g., program code 714) embodied on a computer-readablemedium may be transmitted using any appropriate medium, including butnot limited to wireless, wireline, optical fiber cable, RF, etc., or anysuitable combination of the foregoing.

Computer program code (e.g., program code 714) for carrying outoperations for aspects of the present invention may be written in anycombination of one or more programming languages, including an objectoriented programming language such as Java®, Smalltalk, C++ or the likeand conventional procedural programming languages, such as the “C”programming language or similar programming languages. Java and allJava-based trademarks and logos are trademarks or registered trademarksof Oracle and/or its affiliates. Instructions of the program code may becarried out entirely on a user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server, where the aforementioned user's computer, remotecomputer and server may be, for example, computer system 102 or anothercomputer system (not shown) having components analogous to thecomponents of computer system 102 included in FIG. 7. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network (not shown), including a LAN or a WAN, orthe connection may be made to an external computer (e.g., through theInternet using an Internet Service Provider).

Aspects of the present invention are described herein with reference toflowchart illustrations (e.g., FIGS. 2A-2B, FIG. 3, FIGS. 4A-4B, FIG. 5and FIG. 6) and/or block diagrams of methods, apparatus (systems) (e.g.,FIG. 1 and FIG. 7), and computer program products according toembodiments of the invention. It will be understood that each block ofthe flowchart illustrations and/or block diagrams, and combinations ofblocks in the flowchart illustrations and/or block diagrams, can beimplemented by computer program instructions (e.g., program code 714).These computer program instructions may be provided to one or morehardware processors (e.g., CPU 702) of a general purpose computer,special purpose computer, or other programmable data processingapparatus to produce a machine, such that the instructions, which arecarried out via the processor(s) of the computer or other programmabledata processing apparatus, create means for implementing thefunctions/acts specified in the flowcharts and/or block diagram block orblocks.

These computer program instructions may also be stored in acomputer-readable medium (e.g., memory 704 or computer data storage unit712) that can direct a computer (e.g., computer system 102), otherprogrammable data processing apparatus, or other devices to function ina particular manner, such that the instructions (e.g., program 714)stored in the computer-readable medium produce an article of manufactureincluding instructions which implement the function/act specified in theflowcharts and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer(e.g., computer system 102), other programmable data processingapparatus, or other devices to cause a series of operational steps to beperformed on the computer, other programmable apparatus, or otherdevices to produce a computer implemented process such that theinstructions (e.g., program 714) which are carried out on the computer,other programmable apparatus, or other devices provide processes forimplementing the functions/acts specified in the flowcharts and/or blockdiagram block or blocks.

Any of the components of an embodiment of the present invention can bedeployed, managed, serviced, etc. by a service provider that offers todeploy or integrate computing infrastructure with respect to testing aconfiguration change. Thus, an embodiment of the present inventiondiscloses a process for supporting computer infrastructure, wherein theprocess comprises a first computer system providing at least one supportservice for at least one of integrating, hosting, maintaining anddeploying computer-readable code (e.g., program code 714) in a secondcomputer system (e.g., computer system 102) comprising one or moreprocessors (e.g., CPU 702), wherein the processor(s) carry outinstructions contained in the code causing the second computer system totest a configuration change.

In another embodiment, the invention provides a method that performs theprocess steps of the invention on a subscription, advertising and/or feebasis. That is, a service provider, such as a Solution Integrator, canoffer to create, maintain, support, etc. a process of testing aconfiguration change. In this case, the service provider can create,maintain, support, etc. a computer infrastructure that performs theprocess steps of the invention for one or more customers. In return, theservice provider can receive payment from the customer(s) under asubscription and/or fee agreement, and/or the service provider canreceive payment from the sale of advertising content to one or morethird parties.

The flowcharts in FIGS. 2A-2B, FIG. 3, FIGS. 4A-4B, FIG. 5 and FIG. 6and the block diagrams in FIG. 1 and FIG. 7 illustrate the architecture,functionality, and operation of possible implementations of systems,methods, and computer program products according to various embodimentsof the present invention. In this regard, each block in the flowchartsor block diagrams may represent a module, segment, or portion of code(e.g., program code 714), which comprises one or more executableinstructions for implementing the specified logical function(s). Itshould also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in thefigures. For example, two blocks shown in succession may, in fact, beperformed substantially concurrently, or the blocks may sometimes beperformed in reverse order, depending upon the functionality involved.It will also be noted that each block of the block diagrams and/orflowchart illustrations, and combinations of blocks in the blockdiagrams and/or flowchart illustrations, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and computerinstructions.

While embodiments of the present invention have been described hereinfor purposes of illustration, many modifications and changes will becomeapparent to those skilled in the art. Accordingly, the appended claimsare intended to encompass all such modifications and changes as fallwithin the true spirit and scope of this invention.

What is claimed is:
 1. A method of testing a change in a configurationof a computing environment, the method comprising the steps of: acomputer determining a first set of one or more configurable attributesof a first user identifier (ID) of a first user in the computingenvironment, the first user ID having been received from a second userlogged into the computing environment using a second user ID providingthe second user with an authority of an administrator in the computingenvironment; the computer generating a temporary user ID having a secondset of one or more configurable attributes so that values of respectiveconfigurable attributes in the first and second sets of configurableattributes are identical; the computer associating the change in theconfiguration with the temporary user ID and with no other user ID; andbased on the change in the configuration being associated with thetemporary user ID and with no other user ID, the computer performing asimulation with the change in the configuration applied in the computingenvironment, the change in the configuration not affecting the first andsecond user IDs.
 2. The method of claim 1, wherein the step ofperforming the simulation comprises the step of the computer trackingmodifications of data records made by the temporary user ID.
 3. Themethod of claim 2, wherein the step of tracking modifications of datarecords made by the temporary user ID includes the steps of: thecomputer determining the temporary user ID initiates an update of a datarecord included in the data records; in response to the step ofdetermining the temporary user ID initiates the update, the computerexporting the data record into a temporary file; and the computerupdating the data record.
 4. The method of claim 2, wherein the step oftracking modifications of data records made by the temporary user IDincludes the steps of: the computer determining the temporary user IDinitiates a deletion of a data record included in the data records; inresponse to the step of determining the temporary user ID initiates thedeletion, the computer exporting the data record into a temporary file;and the computer deleting the data record.
 5. The method of claim 2,wherein the step of tracking modifications of data records made by thetemporary user ID includes the steps of: the computer determining thetemporary user ID initiates an insertion of a data record into adatabase; in response to the step of determining the temporary user IDinitiates the insertion, the computer performing the insertion of thedata record into the database; and the computer storing a primary keyand database table of the inserted data record in a temporary file. 6.The method of claim 2, further comprising the step of the computerundoing the modifications of the data records, wherein the step ofundoing comprises: the computer determining whether each modification ofthe data records applies to transactional data; if a modification of adata record included in the modifications of the data records applies totransactional data, the computer setting the status of the data recordto canceled; if the modification of the data record included in themodifications of the data records does not apply to transactional data,the computer determining whether the modification was an update or adeletion of the data record that was exported into a temporary file, orwhether the modification was an insertion of the data record into adatabase; if the modification was the update or the deletion, thecomputer importing the exported data record from the temporary file; andif the modification was the insertion, the computer deleting theinserted data record based on a primary key and database table of theinserted data record.
 7. The method of claim 1, further comprising thesteps of: the computer determining the second user requires aninvocation of an action in the simulation as the first user ID ratherthan as the temporary user ID; the computer determining that the firstuser is logged in with the first user ID; the computer presenting awarning to the first user about an automatic log out of the first userID after a time period elapses; after the time period elapses, thecomputer automatically logging out the first user ID; the computerdisallowing the first user ID from logging in during the simulation; thecomputer intercepting a dynamically generated command to invoke theaction during the simulation; the computer replacing the temporary userID with the first user ID in the dynamically generated command; thecomputer receiving another command to end the simulation; and subsequentto the step of receiving the other command to end the simulation, thecomputer allowing the first user ID to log in.
 8. The method of claim 1,wherein the step of the computer associating the change in theconfiguration with the temporary user ID and with no other user IDincludes: the computer receiving the change in the configuration and thetemporary user ID to which the change in the configuration applies; thecomputer determining the simulation is active; the computer interceptingan instance of an application that uses the configuration being changedby the change in the configuration; the computer determining a userlogged into the application matches the temporary user ID; the computerperforming a dynamically generated command using the change in theconfiguration; the computer receiving a command to make the change inthe configuration permanent; the computer making the change in theconfiguration permanent; subsequent to the step of making the change inthe configuration permanent, the computer determining no simulation of auser ID is active; and the computer halting interception of any instanceof the application that uses the configuration.
 9. A computer systemcomprising: a central processing unit (CPU); a memory coupled to theCPU; a computer-readable, tangible storage device coupled to the CPU,the storage device containing instructions that, when carried out by theCPU via the memory, implement a method of testing a change in aconfiguration of a computing environment, the method comprising thesteps of: the computer system determining a first set of one or moreconfigurable attributes of a first user identifier (ID) of a first userin the computing environment, the first user ID having been receivedfrom a second user logged into the computing environment using a seconduser ID providing the second user with an authority of an administratorin the computing environment; the computer system generating a temporaryuser ID having a second set of one or more configurable attributes sothat values of respective configurable attributes in the first andsecond sets of configurable attributes are identical; the computersystem associating the change in the configuration with the temporaryuser ID and with no other user ID; and based on the change in theconfiguration being associated with the temporary user ID and with noother user ID, the computer system performing a simulation with thechange in the configuration applied in the computing environment, thechange in the configuration not affecting the first and second user IDs.10. The computer system of claim 9, wherein the step of performing thesimulation comprises the step of the computer system trackingmodifications of data records made by the temporary user ID.
 11. Thecomputer system of claim 10, wherein the step of tracking modificationsof data records made by the temporary user ID includes the steps of: thecomputer system determining the temporary user ID initiates an update ofa data record included in the data records; in response to the step ofdetermining the temporary user ID initiates the update, the computersystem exporting the data record into a temporary file; and the computersystem updating the data record.
 12. The computer system of claim 10,wherein the step of tracking modifications of data records made by thetemporary user ID includes the steps of: the computer system determiningthe temporary user ID initiates a deletion of a data record included inthe data records; in response to the step of determining the temporaryuser ID initiates the deletion, the computer system exporting the datarecord into a temporary file; and the computer system deleting the datarecord.
 13. The computer system of claim 10, wherein the step oftracking modifications of data records made by the temporary user IDincludes the steps of: the computer system determining the temporaryuser ID initiates an insertion of a data record into a database; inresponse to the step of determining the temporary user ID initiates theinsertion, the computer system performing the insertion of the datarecord into the database; and the computer system storing a primary keyand database table of the inserted data record in a temporary file. 14.The computer system of claim 10, wherein the method further comprisesthe step of the computer system undoing the modifications of the datarecords, wherein the step of undoing comprises: the computer systemdetermining whether each modification of the data records applies totransactional data; if a modification of a data record included in themodifications of the data records applies to transactional data, thecomputer system setting the status of the data record to canceled; ifthe modification of the data record included in the modifications of thedata records does not apply to transactional data, the computer systemdetermining whether the modification was an update or a deletion of thedata record that was exported into a temporary file, or whether themodification was an insertion of the data record into a database; if themodification was the update or the deletion, the computer systemimporting the exported data record from the temporary file; and if themodification was the insertion, the computer system deleting theinserted data record based on a primary key and database table of theinserted data record.
 15. A computer program product comprising: acomputer-readable, tangible storage device; and computer-readableprogram instructions stored in the computer-readable, tangible storagedevice, the computer-readable program instructions, when carried out bya central processing unit (CPU) of a computer system, implement a methodof testing a change in a configuration of a computing environment, themethod comprising the steps of: the computer system determining a firstset of one or more configurable attributes of a first user identifier(ID) of a first user in the computing environment, the first user IDhaving been received from a second user logged into the computingenvironment using a second user ID providing the second user with anauthority of an administrator in the computing environment; the computersystem generating a temporary user ID having a second set of one or moreconfigurable attributes so that values of respective configurableattributes in the first and second sets of configurable attributes areidentical; the computer system associating the change in theconfiguration with the temporary user ID and with no other user ID; andbased on the change in the configuration being associated with thetemporary user ID and with no other user ID, the computer systemperforming a simulation with the change in the configuration applied inthe computing environment, the change in the configuration not affectingthe first and second user IDs.
 16. The computer program product of claim15, wherein the step of performing the simulation comprises the step ofthe computer system tracking modifications of data records made by thetemporary user ID.
 17. The computer program product of claim 16, whereinthe step of tracking modifications of data records made by the temporaryuser ID includes the steps of: the computer system determining thetemporary user ID initiates an update of a data record included in thedata records; in response to the step of determining the temporary userID initiates the update, the computer system exporting the data recordinto a temporary file; and the computer system updating the data record.18. The computer program product of claim 16, wherein the step oftracking modifications of data records made by the temporary user IDincludes the steps of: the computer system determining the temporaryuser ID initiates a deletion of a data record included in the datarecords; in response to the step of determining the temporary user IDinitiates the deletion, the computer system exporting the data recordinto a temporary file; and the computer system deleting the data record.19. The computer program product of claim 16, wherein the step oftracking modifications of data records made by the temporary user IDincludes the steps of: the computer system determining the temporaryuser ID initiates an insertion of a data record into a database; inresponse to the step of determining the temporary user ID initiates theinsertion, the computer system performing the insertion of the datarecord into the database; and the computer system storing a primary keyand database table of the inserted data record in a temporary file. 20.The computer program product of claim 16, wherein the method furthercomprises the step of the computer system undoing the modifications ofthe data records, wherein the step of undoing comprises: the computersystem determining whether each modification of the data records appliesto transactional data; if a modification of a data record included inthe modifications of the data records applies to transactional data, thecomputer system setting the status of the data record to canceled; ifthe modification of the data record included in the modifications of thedata records does not apply to transactional data, the computer systemdetermining whether the modification was an update or a deletion of thedata record that was exported into a temporary file, or whether themodification was an insertion of the data record into a database; if themodification was the update or the deletion, the computer systemimporting the exported data record from the temporary file; and if themodification was the insertion, the computer system deleting theinserted data record based on a primary key and database table of theinserted data record.